home *** CD-ROM | disk | FTP | other *** search
-
-
-
- lllloooocccckkkkdddd((((1111MMMM)))) lllloooocccckkkkdddd((((1111MMMM))))
-
-
-
- NNNNAAAAMMMMEEEE
- lockd - NFS lock daemon
-
- SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
- ////uuuussssrrrr////eeeettttcccc////rrrrppppcccc....lllloooocccckkkkdddd [ ----gggg _g_r_a_c_e_p_e_r_i_o_d ] [ ----llll ] [ _n_s_e_r_v_e_r_s ]
-
- DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
- _l_o_c_k_d provides the inherently stateful locking services within the
- stateless NFS environment. It allows the locking of records and files
- between applications running on different physical machines sharing the
- same filesystems mounted with NFS. _n_s_e_r_v_e_r_s is the number of lockd
- servers to start.
-
- Locks are presently advisory only. The lock style implemented by _l_o_c_k_d
- is that specified in the SVID (see _l_o_c_k_f(3C) and _f_c_n_t_l(2)). There is no
- interaction between the _l_o_c_k_d's locks and _f_l_o_c_k(3B) style locks.
-
- _l_o_c_k_d is started during system initialization if the _c_h_k_c_o_n_f_i_g(1M) lllloooocccckkkkdddd
- flag is set on. Command-line options belong in
- /_e_t_c/_c_o_n_f_i_g/_l_o_c_k_d._o_p_t_i_o_n_s.
-
- If _n_f_s_d(1M) is running, _l_o_c_k_d registers its RPC services and exits,
- leaving _n_f_s_d to handle the requests.
-
- _l_o_c_k_d processes lock requests that are either sent locally by the kernel
- or remotely by another lock daemon. In the case of local lock requests
- for remote data, _l_o_c_k_d forwards the lock requests to the server site's
- lock daemon through the _R_P_C/_X_D_R(3R) package. _l_o_c_k_d then requests the
- local status monitor daemon, _s_t_a_t_d(1M), for monitor service of the
- server. The reply to the lock request is not sent to the kernel until
- the status daemon and the server site's lock daemon have replied.
-
- When a server recovers, it waits for a grace period for all client site
- _l_o_c_k_ds to submit reclaim requests. Client site _l_o_c_k_ds are notified by
- the _s_t_a_t_d of the server recovery and promptly resubmit previously granted
- lock requests. If a _l_o_c_k_d fails to secure a previously granted lock at
- the server site, it sends SIGUSR1 to the application process. The
- process must explicitly handle this signal if the loss of a lock should
- cause it to terminate.
-
- OOOOPPPPTTTTIIIIOOOONNNNSSSS
- ----gggg _g_r_a_c_e_p_e_r_i_o_d _l_o_c_k_d uses _g_r_a_c_e_p_e_r_i_o_d (seconds) as the grace period
- duration instead of the default value (see TTTTUUUUNNNNIIIINNNNGGGG
- below).
-
- ----llll Set SVID locks for files which are locked by DOS
- machines running PC-NFS and compatible file sharing
- utilities. Normally, _l_o_c_k_d does not set SVID locks for
- such requests.
-
-
-
-
-
-
- PPPPaaaaggggeeee 1111
-
-
-
-
-
-
- lllloooocccckkkkdddd((((1111MMMM)))) lllloooocccckkkkdddd((((1111MMMM))))
-
-
-
- TTTTUUUUNNNNIIIINNNNGGGG
- _l_o_c_k_d has four tunable parameters: _l_o_c_k_d__g_r_a_c_e__p_e_r_i_o_d,
- _l_o_c_k__s_h_a_r_e__r_e_q_u_e_s_t_s, _n_l_m__g_r_a_n_t_e_d__t_i_m_e_o_u_t, and _n_l_m__m_a_x_d_u_p_r_e_q_s.
- _l_o_c_k_d__g_r_a_c_e__p_e_r_i_o_d controls the starup grace period for the reclaiming of
- locks. This was previously controlled by the -g command line option.
- _L_o_c_k__s_h_a_r_e__r_e_q_u_e_s_t_s tells _l_o_c_k_d to preform UNIX file locking for share
- and unshare requests. _N_l_m__g_r_a_n_t_e_d__t_i_m_e_o_u_t controls the timeout used in
- making NLM_GRANTED and NLMPROC_GRANTED callbacks for blocked lock
- requests which have been granted. This value is specified in tenths of a
- second. _N_l_m__m_a_x_d_u_p_r_e_q_s controls how many NLM RPC duplicate request cache
- entries are allocated. The default setting is 0. This causes the
- allocation to be sized based upon the memory size of the system.
-
- NNNNOOOOTTTTEEEESSSS
- The reply to a lock request for remote data is delayed until all daemons
- become available.
-
- In the Sun implementation, _l_o_c_k_d sends SIGLOST. when a lock is lost.
- The IRIX implementation sends SIGUSR1. Programs should establish a
- signal handler to catch this signal and exit.
-
- For client operations, _l_o_c_k_d is no longer used as the intermediary for
- NLM RPCs. The kernel makes the RPCs to the server directly. These calls
- all use UDP. There is no support for TCP as a transport for NLM RPCs on
- the client side.
-
- Since NLM RPCs are handled by the NFS server _n_f_s_d, both TCP and UDP are
- accepted as transports on the server side. For blocked lock requests,
- however, the NLM_GRANTED or NLM_GRANTED_MSG RPC will be sent using UDP
- regardless of what transport the client used.
-
- SSSSEEEEEEEE AAAALLLLSSSSOOOO
- statd(1M), fcntl(2), signal(2), lockf(3C).
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- PPPPaaaaggggeeee 2222
-
-
-
-